Thanks for this @mkoeppe and sorry for the delay in looking at it. I just glanced at it now and it looks good, but there are some failing test. Glancing at those, they look to be CVXPy issues, not CyLP issues. Any ideas how to get then passing?

they look to be CVXPy issues, not CyLP issues. Any ideas how to get then passing?

I'd suggest to run the GH Actions workflow on the master branch to check the baseline. I'm not sure if we're pinning CVXPy for these tests; likely it's caused by a CVXPy update or other updated packages

Indeed, the result is the same in master. The problem seems to be cvxpy is being imported from site-packages (/Library/Frameworks/Python.framework/.../cvxpy), but pytest is trying to collect tests from the local development directory (/Users/runner/work/CyLP/CyLP/cvxpy). This creates a conflict because the same module exists in both places. But I don't really know what changed because it looks like it should not have been working before either. I opened #224 to try to fix this.

Indeed, running the tests from the installed cvxpy with python -m pytest --pyargs cvxpy.tests fixed the issue. But cvxpy requires numpy 2 now, while we were explicitly testing CyLP with numpy 1.26 just for good measure. So testing with numpy 1.26 is now failing because of dependency conflicts. I think it is easy to allow backwards compatibility with older numpy versions, so I wish cvxpy had done that, but I guess I can just disable that test for now.

I merged #224 and then tried to rebase your branch, but for some reason, I can't push to it, even though this PR is open. Instead, I just opened and closed the PR to re-run tests. If you want to rebase on master and force push, that might be cleaner.

Rebased.

I merged #224 and then tried to rebase your branch, but for some reason, I can't push to it

Might be because I opened the PR from an org repository, rather than a personal repository

Looks good now!